Storage systems and aliased memory

ABSTRACT

Aspects of the subject matter described herein relate to storage systems and aliased memory. In aspects, a file system driver or other component may send a request to a memory controller to create an alias between two blocks of memory. One of the blocks of memory may be used for main memory while the other of the blocks of memory may be used for a storage system. In response, the memory controller may create an alias between the blocks of memory. Until the alias is severed, when the memory controller receives a request for data from the block in main memory, the memory controller may respond with data from the memory block used for the storage system. The memory controller may also implement other actions as described herein.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/036,298 filed Sep. 25, 2013, which claims the benefit of U.S.Provisional Application No. 61/828,636, filed May 29, 2013, both ofwhich are hereby incorporated by reference herein in their entirety.

BACKGROUND

Memory for a computer system has traditionally been divided intovolatile and nonvolatile memory. Volatile memory requires power tomaintain data stored thereon. Nonvolatile memory can retain data evenwhen not powered. Previously, computers have used both volatile andnonvolatile memory because each has certain advantages. For example,volatile memory is typically much faster than nonvolatile memory whilenonvolatile memory often costs much less per bit. Advances innonvolatile memory technology are closing the gap in speed betweenvolatile and nonvolatile memory while nonvolatile memory maintains theadvantage of preserving data during power loss.

The subject matter claimed herein is not limited to embodiments thatsolve any disadvantages or that operate only in environments such asthose described above. Rather, this background is only provided toillustrate one exemplary technology area where some embodimentsdescribed herein may be practiced.

SUMMARY

Briefly, aspects of the subject matter described herein relate tostorage systems and aliased memory. In aspects, a file system driver orother component may send a request to a memory controller to create analias between two blocks of memory. One of the blocks of memory may beused for main memory while the other of the blocks of memory may be usedfor a storage system. In response, the memory controller may create analias between the blocks of memory. Until the alias is severed, when thememory controller receives a request for data from the block in mainmemory, the memory controller may respond with data from the memoryblock used for the storage system. The memory controller may alsoimplement other actions as described herein.

This Summary is provided to briefly identify some aspects of the subjectmatter that is further described below in the Detailed Description. ThisSummary is not intended to identify key or essential features of theclaimed subject matter, nor is it intended to be used to limit the scopeof the claimed subject matter.

The phrase “subject matter described herein” refers to subject matterdescribed in the Detailed Description unless the context clearlyindicates otherwise. The term “aspects” should be read as “at least oneaspect.” Identifying aspects of the subject matter described in theDetailed Description is not intended to identify key or essentialfeatures of the claimed subject matter.

The aspects described above and other aspects of the subject matterdescribed herein are illustrated by way of example and not limited inthe accompanying figures in which like reference numerals indicatesimilar elements and in which:

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram representing an exemplary general-purposecomputing environment into which aspects of the subject matter describedherein may be incorporated;

FIGS. 2 and 5 are block diagrams that generally represent nonvolatilememory in accordance with aspects of the subject matter describedherein;

FIG. 3 is a block diagram that generally represents various states ofaliases between sub blocks of the memory blocks of FIG. 2 in accordancewith aspects of the subject matter described herein;

FIGS. 4 and 6 are block diagrams that generally represents exemplarycomponents of systems configured in accordance with aspects of thesubject matter described herein;

FIG. 7 is a flow diagram that generally represents exemplary actionsthat may occur in conjunction with creating an alias from a memorycontroller perspective in accordance with aspects of the subject matterdescribed herein;

FIG. 8 is a flow diagram that generally represents exemplary actionsthat may occur in conjunction with obtaining data for an aliased blockfrom a memory controller perspective in accordance with aspects of thesubject matter described herein; and

FIG. 9 is a flow diagram that shows exemplary actions that may occur ona component accessing memory via a memory controller in accordance withaspects of the subject matter described herein.

DETAILED DESCRIPTION Definitions

As used herein, the term “includes” and its variants are to be read asopen-ended terms that mean “includes, but is not limited to.” The term“or” is to be read as “and/or” unless the context clearly dictatesotherwise. The term “based on” is to be read as “based at least in parton.” The terms “one embodiment” and “an embodiment” are to be read as“at least one embodiment.” The term “another embodiment” is to be readas “at least one other embodiment.”

As used herein, terms such as “a,” “an,” and “the” are inclusive of oneor more of the indicated item or action. In particular, in the claims areference to an item generally means at least one such item is presentand a reference to an action means at least one instance of the actionis performed.

Sometimes herein the terms “first,” “second,” “third,” and so forth maybe used. Without additional context, the use of these terms in theclaims is not intended to imply an ordering but is rather used foridentification purposes. For example, the phrases “first version” and“second version” do not necessarily mean that the first version is thevery first version or was created before the second version or even thatthe first version is requested or operated on before the second version.Rather, these phrases are used to identify different versions.

Headings are for convenience only; information on a given topic may befound outside the section whose heading indicates that topic.

Other definitions, explicit and implicit, may be included below.

Exemplary Operating Environment

FIG. 1 illustrates an example of a suitable computing system environment100 on which aspects of the subject matter described herein may beimplemented. The computing system environment 100 is only one example ofa suitable computing environment and is not intended to suggest anylimitation as to the scope of use or functionality of aspects of thesubject matter described herein. Neither should the computingenvironment 100 be interpreted as having any dependency or requirementrelating to any one or combination of components illustrated in theexemplary operating environment 100.

Aspects of the subject matter described herein are operational withnumerous other general purpose or special purpose computing systemenvironments or configurations. Examples of well-known computingsystems, environments, or configurations that may be suitable for usewith aspects of the subject matter described herein comprise personalcomputers, server computers—whether on bare metal or as virtualmachines—, hand-held or laptop devices, multiprocessor systems,microcontroller-based systems, set-top boxes, programmable andnon-programmable consumer electronics, network PCs, minicomputers,mainframe computers, personal digital assistants (PDAs), gaming devices,printers, appliances including set-top, media center, or otherappliances, automobile-embedded or attached computing devices, othermobile devices, phone devices including cell phones, wireless phones,and wired phones, distributed computing environments that include any ofthe above systems or devices, and the like. While various embodimentsmay be limited to one or more of the above devices, the term computer isintended to cover the devices above unless otherwise indicated.

Aspects of the subject matter described herein may be described in thegeneral context of computer-executable instructions, such as programmodules, being executed by a computer. Generally, program modulesinclude routines, programs, objects, components, data structures, and soforth, which perform particular tasks or implement particular abstractdata types. Aspects of the subject matter described herein may also bepracticed in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules may be located in both local and remote computer storage mediaincluding memory storage devices.

Alternatively, or in addition, the functionality described herein may beperformed, at least in part, by one or more hardware logic components.For example, and without limitation, illustrative types of hardwarelogic components that can be used include Field-programmable Gate Arrays(FPGAs), Program-specific Integrated Circuits (ASICs), Program-specificStandard Products (ASSPs), System-on-a-chip systems (SOCs), ComplexProgrammable Logic Devices (CPLDs), and the like.

With reference to FIG. 1, an exemplary system for implementing aspectsof the subject matter described herein includes a general-purposecomputing device in the form of computer 110. A computer may include anyelectronic device that is capable of executing an instruction.Components of the computer 110 may include a processing unit 120, asystem memory 130, and one or more system buses (represented by systembus 121) that couples various system components including the systemmemory to the processing unit 120. The system bus 121 may be any ofseveral types of bus structures including a memory bus or memorycontroller, a peripheral bus, and a local bus using any of a variety ofbus architectures. By way of example, and not limitation, sucharchitectures include Industry Standard Architecture (ISA) bus, MicroChannel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, Peripheral ComponentInterconnect (PCI) bus also known as Mezzanine bus, Peripheral ComponentInterconnect Extended (PCI-X) bus, Advanced Graphics Port (AGP), and PCIexpress (PCie).

The processing unit 120 may be connected to a hardware security device122. The security device 122 may store and be able to generatecryptographic keys that may be used to secure various aspects of thecomputer 110. In one embodiment, the security device 122 may comprise aTrusted Platform Module (TPM) chip, TPM Security Device, or the like.

The computer 110 typically includes a variety of computer-readablemedia. Computer-readable media can be any available media that can beaccessed by the computer 110 and includes both volatile and nonvolatilemedia, and removable and non-removable media. By way of example, and notlimitation, computer-readable media may comprise computer storage mediaand communication media.

Computer storage media includes both volatile and nonvolatile, removableand non-removable media implemented in any method or technology forstorage of information such as computer-readable instructions, datastructures, program modules, or other data. Computer storage mediaincludes RAM, ROM, EEPROM, solid state storage, flash memory or othermemory technology, CD-ROM, digital versatile discs (DVDs), Blu-ray Disc(BD) or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by the computer 110. Computer storage media does not includecommunication media.

Communication media typically embodies computer-readable instructions,data structures, program modules, or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of any ofthe above should also be included within the scope of computer-readablemedia.

The system memory 130 may include computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 131and random access memory (RAM)

132. Nonvolatile memory may be substituted for some or all of the ROM131 and/or the RAM 132. For example, memristor memory, phase-changememory (PCM), or some other type of nonvolatile memory may be usedinstead of, or in addition to, the ROM 131 and/ or the RAM 132.

A basic input/output system 133 (BIOS), containing the basic routinesthat help to transfer information between elements within computer 110,such as during start-up, is typically stored in ROM 131. RAM 132typically contains data and/or program modules that are immediatelyaccessible to and/or presently being operated on by processing unit 120.By way of example, and not limitation, FIG. 1 illustrates operatingsystem 134, application programs 135, other program modules 136, andprogram data 137.

The computer 110 may also include other removable/non-removable,volatile/nonvolatile computer storage media. By way of example only,FIG. 1 illustrates a hard disk drive 141 that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive 151that reads from or writes to a removable, nonvolatile magnetic disk 152,and an optical disc drive 155 that reads from or writes to a removable,nonvolatile optical disc 156 such as a CD ROM, DVD, BD, or other opticalmedia.

In one implementation, memristor memory, phase-change memory, or someother type of nonvolatile memory may be used instead of, or in additionto, the hard drive 141.

Other removable/non-removable, volatile/nonvolatile computer storagemedia that can be used in the exemplary operating environment includemagnetic tape cassettes, flash memory cards and other solid statestorage devices, digital versatile discs, other optical discs, digitalvideo tape, solid state RAM, solid state ROM, and the like. The harddisk drive 141 may be connected to the system bus 121 through theinterface 140, and magnetic disk drive 151 and optical disc drive 155may be connected to the system bus 121 by an interface for removablenonvolatile memory such as the interface 150.

The drives and their associated computer storage media, discussed aboveand illustrated in FIG. 1, provide storage of computer-readableinstructions, data structures, program modules, and other data for thecomputer 110. In FIG. 1, for example, hard disk drive 141 is illustratedas storing operating system 144, application programs 145, other programmodules 146, and program data 147. Note that these components can eitherbe the same as or different from operating system 134, applicationprograms 135, other program modules 136, and program data 137. Operatingsystem 144, application programs 145, other program modules 146, andprogram data 147 are given different numbers herein to illustrate thatthey may be different copies.

A user may enter commands and information into the computer 110 throughinput devices such as a keyboard 162 and pointing device 161, commonlyreferred to as a mouse, trackball, or touch pad. Other input devices(not shown) may include a microphone (e.g., for inputting voice or otheraudio), joystick, game pad, satellite dish, scanner, a touch-sensitivescreen, a writing tablet, a camera (e.g., for inputting gestures orother visual input), or the like. These and other input devices areoften connected to the processing unit 120 through a user inputinterface 160 that is coupled to the system bus, but may be connected byother interface and bus structures, such as a parallel port, game portor a universal serial bus (USB).

Through the use of one or more of the above-identified input devices aNatural User Interface (NUI) may be established. A NUI, may rely onspeech recognition, touch and stylus recognition, gesture recognitionboth on screen and adjacent to the screen, air gestures, head and eyetracking, voice and speech, vision, touch, gestures, machineintelligence, and the like. Some exemplary NUI technology that may beemployed to interact with a user include touch sensitive displays, voiceand speech recognition, intention and goal understanding, motion gesturedetection using depth cameras (such as stereoscopic camera systems,infrared camera systems, RGB camera systems, and combinations thereof),motion gesture detection using accelerometers/gyroscopes, facialrecognition, 3D displays, head, eye, and gaze tracking, immersiveaugmented reality and virtual reality systems, as well as technologiesfor sensing brain activity using electric field sensing electrodes (EEGand related methods).

A monitor 191 or other type of display device is also connected to thesystem bus 121 via an interface, such as a video interface 190. Inaddition to the monitor, computers may also include other peripheraloutput devices such as speakers 197 and printer 196, which may beconnected through an output peripheral interface 195.

The computer 110 may operate in a networked environment using logicalconnections to one or more remote computers, such as a remote computer180. The remote computer 180 may be a personal computer, a server, arouter, a network PC, a peer device or other common network node, andtypically includes many or all of the elements described above relativeto the computer 110, although only a memory storage device 181 has beenillustrated in FIG. 1. The logical connections depicted in FIG. 1include a local area network (LAN) 171 and a wide area network (WAN)173, but may also include phone networks, near field networks, and othernetworks. Such networking environments are commonplace in offices,enterprise-wide computer networks, intranets, and the Internet.

When used in a LAN networking environment, the computer 110 is connectedto the LAN 171 through a network interface or adapter 170. When used ina WAN networking environment, the computer 110 may include a modem 172or other means for establishing communications over the WAN 173, such asthe Internet. The modem 172, which may be internal or external, may beconnected to the system bus 121 via the user input interface 160 orother appropriate mechanism. In a networked environment, program modulesdepicted relative to the computer 110, or portions thereof, may bestored in the remote memory storage device. By way of example, and notlimitation, FIG. 1 illustrates remote application programs 185 asresiding on memory device 181. It will be appreciated that the networkconnections shown are exemplary and other means of establishing acommunications link between the computers may be used.

Nonvolatile Memory

As mentioned previously, advances are being made in nonvolatile memory.In accordance with aspects of the subject matter described herein, anoperating system may be structured to take advantage of these advances.FIGS. 2 and 5 are block diagrams that generally represent nonvolatilememory in accordance with aspects of the subject matter describedherein. The nonvolatile memory 205 may include an array of memorystorage elements that may be accessed by addresses. In oneimplementation, a memory device that includes the nonvolatile memory 205may be addressed using memory primitives. The memory primitives used toaccess the nonvolatile memory 205 may be similar or identical to thoseused to access volatile memory such as RAM.

Fast nonvolatile memory may be attached to a memory bus. For example,currently, some types of nonvolatile memory perform 2-4 times slowerthan RAM and a couple of orders of magnitude faster than flash memory orhard disk storage. These types of nonvolatile memory may have lowlatency and high data transfer rates that may benefit more by beingattached to a memory bus than being attached to a storage bus.

As illustrated in FIG. 2, the nonvolatile memory 205 has been dividedinto a file system region 210 and a memory region 211. The illustratedsizes of these regions are exemplary only. In other implementations, forexample, these sizes may be greatly varied from the sizes shown in FIG.2.

Furthermore, the nonvolatile memory 205 may be implemented using one ormore subsystems. For example, where multiple types of nonvolatile memoryare hosted on a system or where multiple memory units of the same ordifferent types of nonvolatile memory are hosted on the system, thesystem may include multiple subsystems to access the nonvolatile memory.

Although the term “file system” is sometimes used herein, it is to beunderstood that this term is exemplary only and that the teachingsherein may also be applied to other types of storage systems. A storagesystem may include one or more hardware and/or software components thatorganize data that is persisted.

The size of the file system region 210 and the size of the memory region211 may be set or reset, for example, during a configuration operation.A configuration operation may occur prior to or after installing anoperation system to size or resize memory regions as desired. Anoperating system may be configured to look for configuration data in apredefined location of the nonvolatile memory 205. The configurationdata may indicate how the nonvolatile memory is to be divided betweenfile system data and memory available for other uses.

The memory region 211 is a portion of the nonvolatile memory 205 thathas been set aside to provide additional main memory for a computer.This memory may be used in lieu of, or in addition to, any RAM or othervolatile memory of the computer.

The file system region 210 is a portion of the nonvolatile memory 205that has been set aside for file system data. Although physically,memory elements in this region may be accessed in the same manner asmemory elements in the memory region 211 are accessed, file systemcomponents acting in conjunction with memory hardware may enforcecertain rules regarding these accesses as described in more detailbelow.

In traditional file systems, a block of data from a hard disk may becopied into main memory. Once in main memory, the data may be modified.At some point, the block of data as modified is written from the mainmemory to the hard disk.

In accordance with aspects of the subject matter describe herein, a filesystem may be structured to avoid some of the copying that occurs intraditional file systems. For example, referring to FIG. 2, anapplication may seek to obtain data that is in the block 215. Instead ofcopying the data in the block 215 to memory in the block 216, the filesystem may request that memory hardware create an alias between theblock 216 and the block 215. When an alias is created, an operation thatattempts to read the block 216 obtains the data from the block 215except when certain conditions are met.

After an alias is created, a write to the block 216 causes data to bewritten to the block 216. In one implementation, the memory hardware maywait to copy the data written to the block 216 to the block 215 until atime after the write of the data to the block 216. In anotherimplementation, the memory hardware may wait for an explicit commandfrom the file system before copying the data written to the block 216 tothe block 215. This allows the file system to be more involved whenwrites occur to the nonvolatile memory 205.

Once a write has occurred to the block 216, one or more aliases from theblock 216 to the block 215 may be broken. For example, the block 215 maybe implemented by a plurality of sub blocks. In one implementation, asub block may be a small, fixed-size of memory that can be accessed on amemory architecture that uses the nonvolatile memory 205. In oneimplementation, a block may correspond to a page of memory while a subblock may correspond to a cache line.

In one implementation, when an alias is set up between the block 216 andthe block 215, physically an alias may be set up between each sub blockof the block 216 and its corresponding sub block of the block 215. Thisresults in a plurality of aliases between memory elements of the blocks216 and 215.

In one implementation, when a portion of the block 216 is written to,the sub blocks that include the portion may be determined, and thealiases associated with those sub blocks may be severed. This severingmay occur at any time prior to a subsequent read of the block 216. Whena subsequent read for the block 216 is received, data for the read isretrieved from the block 215 where the aliases have not been severed andfrom block 216 where the aliases have been severed.

In another implementation, when a portion of the block 215 is writtento, the sub blocks that include the portion may be determined, and thealiases associated with those sub blocks may be severed. This severingmay occur at any time prior to a subsequent read of the block 216. Whena subsequent read for the block 216 is received, data for the read isretrieved from the block 215 where the aliases have not been severed andvia block 216 where the aliases have been severed.

In conjunction with severing an alias between a sub block of block 216and a sub block of block 215 and prior to overwriting data in the subblock of block 215, the data in the sub block of block 215 may bepreserved so that it may be obtained when accessing the correspondingsub block of block 216 (or any other sub block that is aliased to thesub block of block 215). Preserving the data may include, for example,copying the data to a location allocated to block 216, copying the datato a new location and updating the alias of block 216 to point to thenew location, keeping the data in its current location and updatingmapping structures associated with block 215 so that a read to block 215obtains the changed data, or the like. This behavior keeps the dataobtainable via block 216 unchanged even when the data of block 215changes.

In one implementation, when a portion of the block 215 is written to orwhen a portion of the block 216 is written to, aliases are broken asoutlined above. In another implementation, aliases are broken inresponse to writing to the block 216, but not in response to writing tothe block

215. In another implementation, aliases are broken in response towriting to the block 215, but not in response to an attempted write tothe block 216. The implementation followed in a particular system may beconfigurable via hardware or software, be hard-wired or hard-coded, orthe like.

FIG. 3 is a block diagram that generally represents various states ofaliases between sub blocks of the memory blocks of FIG. 2 in accordancewith aspects of the subject matter described herein. When an alias isset up between the block 216 and the block 215, this may cause aplurality of aliases to be set up between the sub blocks of block 216and sub blocks of block 215. When a read request for data addressed toblock 216 is received in this state, the read is satisfied from the datain the block 215.

The block 316 represents the block 216 after data has been written tothe block 216. In particular, data has been written to the sub blocks301-303. In conjunction with writing data to create the block 316,aliases for the sub blocks 301-303 have been severed. A read addressedto block

316 will retrieve data from the block 215 where the aliases have notbeen severed and will retrieve data from the block 316 where the aliaseshave been severed (e.g., for sub blocks 301-303). A memory controller(e.g., the memory controller 410 of FIG. 4) may include circuitry forretrieving the data from the appropriate locations taking into accountany aliases that exist.

FIGS. 4 and 6 are block diagrams that generally represents exemplarycomponents of systems configured in accordance with aspects of thesubject matter described herein. The components illustrated in FIGS. 4and 6 are exemplary and are not meant to be all-inclusive of componentsthat may be needed or included. Furthermore, the number of componentsmay differ in other embodiments without departing from the spirit orscope of aspects of the subject matter described herein. In someembodiments, the components described in conjunction with FIGS. 4 and 6may be included in other components (shown or not shown) or placed insubcomponents without departing from the spirit or scope of aspects ofthe subject matter described herein. In some embodiments, the componentsand/or functions described in conjunction with FIGS. 4 and 6 may bedistributed across multiple devices.

The cache 415 may include memory elements that cache data from thenonvolatile memory 205. In one implementation, the cache may comprisedynamic RAM (DRAM), static RAM (SRAM), or some other type of volatile ornonvolatile memory. In some implementations, the cache 415 may beomitted. In some implementations, there may be more than one level ofcache.

The memory controller 410 may include a circuit for accessing data onthe nonvolatile memory 205. Access as used herein may include readingdata, writing data, deleting data, updating data, a combinationincluding two or more of the above, and the like. In one implementation,the memory controller 410 may access the nonvolatile memory 205 usingthe cache 415 only. In other words, in this implementation, whenever thememory controller 410 reads or writes, it may send the read or write tothe cache 415. For a read, the cache 415 may then provide the data fromthe cache 415 if the cache has the data or obtain the data from thenonvolatile memory 205 and then provide the data if the cache does nothave the data. For a write, the cache 415 may store the written data onthe cache 415 and may flush the cache to the nonvolatile memory 205according to caching policies.

In another implementation, the memory controller 410 may also act as acontroller for the cache 415 and may obtain data from the cache 415 orthe nonvolatile memory 205 as appropriate. In this implementation, thememory controller 410 may also cause the cache 415 to write data to thenonvolatile memory 205 according to caching policies.

The memory controller 410 may include an interface by which the filesystem driver 405 may send requests and receive data. In particular,this interface may allow communications including the following:

1. A request to create an alias for the nonvolatile memory. In oneimplementation, the memory controller 410 may be structured to receive arequest to alias a block of memory of the nonvolatile memory 205 toanother block of memory of the nonvolatile memory 205. After receivingthe request, in one implementation, the memory controller 410 may createmultiple aliases if the aliased block spans two or more sub blocks.

In another implementation, the memory controller 410 may only create asingle alias for each alias request. In this implementation, the filesystem driver 405 may be expected to determine how many aliases areneeded for a given block of memory and to communicate with the memorycontroller 410 to establish each of the aliases.

2. A request to read a block of memory. In one implementation, thememory controller 410 may be structured to receive a request to read ablock of memory of the nonvolatile memory 205. If the block includesmemory that is aliased, the memory controller 410 may ensure that thealiased data is obtained from the aliased block (or a cachedrepresentation thereof) . If the block includes memory that is notaliased, the memory controller 410 may ensure that the aliased data isobtained from a non-aliased block (or a cached representation thereof).If a requested block includes both aliased data and non-aliased data,the memory controller 410 may combine the aliased and non-aliased datain conjunction with responding to the request.

3. A request to write to a block of memory. In one implementation, thememory controller 410 may be structured to receive a request to write toa block of memory of the nonvolatile memory 205. If the block of memoryis aliased, the memory controller 410 may ensure that aliases are brokenas appropriate at least prior to providing data in response to a read ofthe aliased block. The memory controller 410 may cause the written datato be written to the cache. The memory controller 410 may flush datafrom the cache periodically, in accordance with caching policies or inresponse to an explicit command from the file system driver 405.

4. A request to copy a block of the nonvolatile memory to anotherlocation of the nonvolatile memory. In one implementation, the memorycontroller 410 may be structured to receive copy commands from the filesystem driver 405. In response to a copy command, the memory controller410 may logically or physically copy the block to another location ofthe nonvolatile memory 205. Physically copying the block to the otherlocation may involve reading data of the block and copying the read datato the other location. Logically copying the block may include, forexample, leaving the data where it is but changing mapping elements sothat the data is returned when requested from the new location.

If portions of the memory to copy are still in the cache 415 and havenot been flushed to the nonvolatile memory 205, this may be handled invarious ways. For example, in one implementation, the memory controller410 may ensure that the data in the cache 415 is copied to thedestination block with or without flushing that data to the sourceblock.

In another implementation, the file system driver 405 may request thatany dirty cache involved in the copy be flushed prior to issuing thecopy command.

5. A request to zero some or all of the nonvolatile memory 205 onrestart. An operating system may use a portion of the nonvolatile memory205 as main memory in addition to or in lieu of using RAM. For example,the operating system may load code and data structures into the memoryregion 211 of FIG. 2. As the nonvolatile memory 205 does not lose dataupon power loss, this code and data may remain even after restarting acomputer that hosts the nonvolatile memory 205. Having data in thememory region 211 upon restart may pose various problems.

In one implementation, the memory controller 410 may be structured toreceive a zero-on-restart request. In response, the memory controller410 may store data indicating this request and, upon restart, logicallyor physically zero out a requested portion of the nonvolatile memory 205(e.g., the memory region 211). Logically zeroing out the requestedportion may involve, for example, flagging that the requested portion iszeroed and then waiting to physically zero a block until a read or writerequest for the block is received. As long as after restart when thefile system driver 405 requests a block marked for zeroing, the filesystem driver 405 receives zeroes for a zeroed block, any implementationthat provides this zeroing functionality may be used without departingfrom the spirit or scope of aspects of the subject matter describedherein.

In one implementation, the memory controller 410 may use hardwareparallelism to zero portions of a block in parallel. This hardwareparallelism may include one or more circuit elements that are able tozero multiple memory elements at the same time.

6. A request to re-alias a block that is currently aliased. An operatingsystem or other process using the nonvolatile memory 205 may, at times,want to move a block in the nonvolatile memory 205 to another locationin the nonvolatile memory 205. This may pose a problem if the memorythat is moved is involved in an alias. For example, referring to FIG. 5,a process may request that the data in the memory block 215 be moved tothe block 505. The memory block 216 may be aliased to point to thememory block 215.

If the alias is not changed to the new block 505, when data in thememory block 215 is changed, a read of data in the memory block 216 mayreturn with the changed data. This may cause problems if, for example,the program expects that the block 216 is still aliased to the data thathas not changed (e.g., the data in block 505).

To address this and other issues, the memory controller 410 may bestructured to receive a request to re-alias a block that is currentlyaliased. For example, in one implementation, the memory controller 410may be structured to receive a request to re-alias memory within aspecified range to memory within another specified range. In thisimplementation, the memory controller 410 may determine all aliases thatpoint to the first specified range and re-alias these aliases to pointto the second specified range. In another implementation, the memorycontroller 410 may be structured to receive a request to re-alias aspecific alias to a new location. For example, referring to FIGS. 3 and4, the memory controller 410 may be structured to receive

a request to re-alias one of the aliases for the sub blocks of block215. In this implementation, when a file system seeks to re-alias a setof aliases for a portion of memory, the file system driver 405 mayinclude logic to determine all aliases for the portion of memory inconjunction with sending commands to re-alias each alias to the memorycontroller 410.

Returning to FIG. 5, when a re-alias request is received and processed,the alias that previously pointed from block 216 to block 215 may bereplaced with an alias that points from block 216 to block 505. A memorycontroller may be structured to perform a re-aliasing operation in a“safe” manner. Safe in this context means that logically the re-aliasingoperation is performed prior to performing other operations that werereceived subsequent to the re-aliasing request. In one implementation,the memory controller may physically perform other operations as long asthe file system driver 405 is unable, using any set of operations, todetect that the re-aliasing operation was performed out-of-orderrelative to when it was received. A memory controller may implementre-aliasing in other ways without departing from the spirit or scope ofaspects of the subject matter described herein. For example, in oneimplementation, a memory controller may be structured to receive a moveblock command and may automatically re-alias aliases that point to theblock when the block is moved.

In another implementation, a memory controller may be structured toreceive a move block command and may modify internal mapping elements tologically move the block without physically copying the block to anotherlocation. In some implementations, moving the block in this way maynegate the need to perform re-aliasing. For example, if an alias pointsto the block regardless of mapping information, then when mappinginformation is changed to move the block, the alias still points at theblock.

In another implementation, a memory controller may be structured toreceive a re-alias command that is not automatically triggered by a moveblock command. In this implementation, the file system driver 405 mayexplicitly request re-aliasing in addition to requesting moving a blockas appropriate.

The above examples are not intended to be all-inclusive or exhaustive ofways in which a memory controller may be structured to implement are-alias command. Based on the teachings herein, those skilled in theart may recognize other implementations that may be used withoutdeparting from the spirit or scope of aspects of the subject matterdescribed herein.

The file system driver 405 may be a software and/or hardware componentthat gives commands and receives responses from the memory controller410. The file system driver 405 may be part of a storage stack of a filesystem and 405 may communicate with the memory controller 410 over asystem bus or other communication link. The file system driver 405 mayprovide an interface to the storage stack of a file system that makesthe nonvolatile memory 205 appear like other storage (e.g., hard disk,flash memory, other nonvolatile or volatile memory, or the like)available to the storage stack.

Although some of the examples herein have described aliases and otheractions regarding nonvolatile memory, the teachings herein may also beapplied to implementations in which the file system region and thememory region are implemented using other memory configurations. Forexample, the file system region and/or the memory region may beimplemented with volatile, nonvolatile, or a combination of volatile andnonvolatile memory. Furthermore, the file system region may beimplemented on a different memory type than the memory region.

In these implementations, the teachings herein may be applied, forexample, to aliases from volatile to volatile memory, aliases fromvolatile to nonvolatile memory, aliases from nonvolatile to volatilememory, systems that have two or more different types of aliases (e.g.,nonvolatile to nonvolatile, volatile to nonvolatile, etc.), and thelike. Furthermore, a memory controller such as the memory controller 410of FIG. 4 may provide an interface that allows aliases to be used,created, re-aliased, and so forth and to perform the other actionsdescribed herein without departing from the spirit or scope of aspectsof the subject matter described herein.

Turning to FIG. 6, the memory controller 605 is shown with an interface610 and exemplary circuits 615-618. In one embodiment, a circuit mayinclude only physical components such as resistor, transistors,capacitors, voltage sources, current sources, switches, inductors, andthe like.

One or more of the physical components may be integrated into one ormore chips. In another embodiment, a circuit may include physicalcomponents together with instructions that indicate how the physicalcomponents are to operate. The instructions may be encoded in volatileor nonvolatile memory.

The circuits of the memory controller 605 are exemplary and are notmeant to be all-inclusive of circuits that may be needed or included.Furthermore, the number of circuits may differ in other embodimentswithout departing from the spirit or scope of aspects of the subjectmatter described herein. In some embodiments, the circuits described inconjunction with FIG. 6 may be included in other circuits or placed insub circuits without departing from the spirit or scope of aspects ofthe subject matter described herein.

The interface 610 may include a structure by which the file systemdriver 405 may communicate with the memory controller 605. For example,the interface 610 may allow the file system driver to communicate withthe memory controller 605 via electrical, optical, or other signals thatencode requests and responses to those requests. The interface 610 mayalso be structured to allow communications as indicated in conjunctionwith FIG. 4.

For example, the interface 610 may be structured to receive a request tocreate an alias between a storage system block of memory and a mainmemory block of memory. A storage system block of memory may be used,for example, in maintaining storage system data and may correspond tothe file system region 210 of FIG. 2 for example. A main memory blockmay be used for main memory of the computer and may correspond to thememory region 211 of FIG. 2.

The aliasing circuit 615 may be structured to create an alias between astorage system block of memory and a main memory block of memory asrequested by the file system driver. As indicated previously, creatingan alias between these memory blocks may include creating a plurality ofaliases between sub blocks of these blocks. The aliasing circuit 615 maybe further structured to sever an alias to a sub block in response to arequest to write to the sub block. In one implementation, the aliasingcircuit 615 may wait to sever the alias to the sub block until justbefore servicing a request to read from the sub block. The aliasingcircuit 615 may also be structured to re-alias an aliased block inresponse to a request to move the aliased block, for example.

The copying circuit 616 may be structured to respond to a request tocopy a main memory block to a new location. In one implementation, thecopying circuit 616 may respond by physically copying data in the mainmemory block to the new location. In another implementation, copyingcircuit 616 may logically copy the data in the main memory block to thenew location by leaving the data in the main memory block and updatingmapping elements as previously described.

The zeroing circuit 618 is structured to respond to a request to zero arequested range of memory. The requested range of memory may includesome or all of memory used for main memory. In one implementation, thezeroing circuit 618 may zero a requested range of the memory by flaggingthat the requested range is zeroed. In one embodiment, the zeroingcircuit 618 may wait to physically zero a portion of the requested rangeuntil a read or write request for the portion is received by the memorycontroller 605. In another embodiment, the zeroing circuit 618 may placezeroes in a read cache in response to a read for memory that has beenflagged as zeroed. In this embodiment, the zeroing circuit 618 may notactually physically zero the flagged range but the read for memory mayreturn zeroes as it is serviced from the read cache. In oneimplementation, the zeroing circuit may wait to zero (e.g., physicallyor logically) the memory until after receiving an indication of restartof a computer hosting the main memory.

The retrieval circuit 617 may be structured to respond to a read requestof the file system driver. Where some aliases have been severed, theretrieval circuit 617 may respond to a request by obtaining first datafrom sub blocks of the storage system block where aliases have not beensevered and to obtain second data from sub blocks of the main memoryblock where aliases have been severed and then combining the first dataand the second data to respond to the read request.

In one example, a main memory block of memory may include a page ofmemory that may be broken into sub blocks where each sub blockcorresponds to a cache line.

FIGS. 7-9 are flow diagrams that generally represent exemplary actionsthat may occur in accordance with aspects of the subject matterdescribed herein. For simplicity of explanation, the methodologydescribed in conjunction with FIGS. 7-9 is depicted and described as aseries of acts. It is to be understood and appreciated that aspects ofthe subject matter described herein are not limited by the actsillustrated and/or by the order of acts. In one embodiment, the actsoccur in an order as described below. In other embodiments, however, twoor more of the acts may occur in parallel or in another order. In otherembodiments, one or more of the actions may occur with other acts notpresented and described herein. Furthermore, not all illustrated actsmay be required to implement the methodology in accordance with aspectsof the subject matter described herein. In addition, those skilled inthe art will understand and appreciate that the methodology couldalternatively be represented as a series of interrelated states via astate diagram or as events.

FIG. 7 is a flow diagram that generally represents exemplary actionsthat may occur in conjunction with creating an alias from a memorycontroller perspective in accordance with aspects of the subject matterdescribed herein. 705, the actions begin.

At block 710, a request to create an alias is received. For example,referring to FIG. 6, the memory controller 605 may receive a request toalias a block of memory via the interface 610. This request may comefrom the file system driver 405. The request may request the creation ofan alias between a storage system block of memory and a main memoryblock of memory.

At block 715, one or more aliases may be created. For example, referringto FIG. 6, the aliasing circuit 615 may create an alias between the twoblocks of memory and/or may create aliases between corresponding subblocks of the two blocks of memory.

At block 720, other actions, if any may be performed. Other actionsinclude, for example, any of the actions described herein with respectto a memory controller.

FIG. 8 is a flow diagram that generally represents exemplary actionsthat may occur in conjunction with obtaining data for an aliased blockfrom a memory controller perspective

in accordance with aspects of the subject matter described herein. Atblock 805, the actions begin.

At block 810, a read request for an aliased block is received. Forexample, referring to FIGS. 2 and 6, the memory controller 605 mayreceive a request to read the data in the block 216. The request maycome from the file system driver 405 and may be communicated via theinterface 610.

In response to the request, data may be obtained from an appropriateblock or sub blocks. For example, referring to FIGS. 3 and 6, if none ofthe aliases between the sub blocks of blocks 216 and 215 has beensevered, then the retrieval circuit 617 may obtain data from the block215. If aliases have been severed as shown in FIG. 3, then the retrievalcircuit 617 may obtain the data from sub blocks of the block 215 wherethe aliased have not been severed and from the sub blocks 301, 302, and303, where the aliases have been severed.

At block 820, data is combined if needed. If some but not all of thealiases of sub blocks have been severed, data from sub blocks that areincluded in different blocks may be combined in response to the request.For example, referring to FIGS. 3 and 6, if none of the aliases betweenthe sub blocks of blocks 216 and 215 have been severed, then theretrieval circuit 617 may have no need to combine sub blocks fromdifferent blocks of memory; otherwise, the retrieval circuit 617 maycombine data from the sub blocks 301, 302, and 303 with data from thesub blocks of block 215 where the aliases have not been severed.

At block 825, the data is provided in response to the request. Forexample, referring to FIG. 6, the memory controller 605 may provide thedata to the file system driver 405 via the interface 610.

At block 830, other actions, if any, may be performed.

FIG. 9 is a flow diagram that shows exemplary actions that may occur ona component accessing memory via a memory controller in accordance withaspects of the subject matter described herein. At block 905, theactions begin.

At block 910, a request to create an alias is sent. For example,referring to FIG. 6, the file system driver 405 may send a request tocreate an alias between two blocks of memory. This request may be sentto the memory controller 605 via the interface 610.

At block 915, after the request to create the alias has been sent, arequest for the aliased data may be sent. For example, referring toFIGS. 2 and 6, the file system driver 405 may send a request addressedto the block 216. This request may also be sent to the memory controller605 via the interface 610.

At block 920, in response to the request, data may be received. Forexample, referring to FIGS. 2 and 6, in response to the requestpreviously sent, the file system driver 405 may receive data that hasbeen obtained from the block 215.

At block 925, other actions, if any, may be performed.

As can be seen from the foregoing detailed description, aspects havebeen described related to storage systems and aliases. While aspects ofthe subject matter described herein are susceptible to variousmodifications and alternative constructions, certain illustratedembodiments thereof are shown in the drawings and have been describedabove in detail. It should be understood, however, that there is nointention to limit aspects of the claimed subject matter to the specificforms disclosed, but on the contrary, the intention is to cover allmodifications, alternative constructions, and equivalents falling withinthe spirit and scope of various aspects of the subject matter describedherein.

What is claimed:
 1. A memory controller configured to: create aliasesbetween sub blocks of a storage system block of memory and correspondingsub blocks of a main memory block of memory; and obtain data from thestorage system block of memory in response to a read request for datafrom the main memory block based at least in part on whether one or moreof the aliases are severed.
 2. The memory controller of claim 1, whereinthe storage system block of memory stores file system data of a filesystem.
 3. The memory controller of claim 1, further comprising aninterface structured to receive a request to create the aliases.
 4. Thememory controller of claim 1, wherein the request is received from afile system driver of an operating system.
 5. The memory controller ofclaim 1, wherein the main memory block of memory comprises a page ofmemory and each sub block of the main memory block of memory comprises acache line.
 6. The memory controller of claim 1, wherein the memorycontroller is further configured to: obtain first data from sub blocksof the storage system block where aliases have not been severed; obtainsecond data from sub blocks of the main memory block where aliases havebeen severed; and combine the first data and the second data in responseto the read request.
 7. The memory controller of claim 1, wherein thememory controller is further configured to sever an alias from a firstsub block to a second sub block in response to a request to write to thefirst sub block or to write to the second sub block.
 8. The memorycontroller of claim 7, wherein the memory controller is furtherconfigured to sever the alias from the first sub block to the second subblock prior to servicing a request to read from the first sub block. 9.The memory controller of claim 1, wherein the memory controller isfurther configured to copy the main memory block to a new location. 10.The memory controller of claim 9, wherein the memory controller isfurther configured to respond to a request to copy the main memory blockto a new location by changing mapping elements and return requested datafrom the new location based on the changed mapping elements.
 11. Thememory controller of claim 1, wherein the memory controller is furtherconfigured to respond to a request to zero a requested range of memorythat includes some or all of the main memory.
 12. The memory controllerof claim 11, wherein the memory controller is further configured torespond to the request to zero a requested range of the memory by:flagging that the requested range is zeroed; and in response to a readrequest that involves the requested range of memory, writing zeroes to aread cache.
 13. The memory controller of claim 11, wherein the memorycontroller is further configured to respond to the request to zero therequested range of the memory by zeroing the requested range of memoryafter receiving an indication of a restart of a computer hosting themain memory.
 14. The memory controller of claim 1, wherein the memorycontroller is further configured to re-alias an aliased block inresponse to a request to move the aliased block.
 15. The memorycontroller of claim 1, wherein the main memory block and the storagesystem block of memory are both included in nonvolatile memory that iscommunicatively couple to a memory bus.
 16. A method implemented atleast in part by a computing device, the method comprising: creatingaliases between corresponding sub blocks of a storage system block ofmemory and a main memory block of memory; and in response to a requestfor data indicating the main memory block of memory, providing the datafrom the storage system block of memory.
 17. The method of claim 16,wherein one of the storage system block of memory or the main memoryblock of memory is included on a nonvolatile memory device and the otherof the storage system block of memory or the main memory block of memoryis included on a volatile memory device.
 18. The method of claim 16,further comprising receiving a request to create the alias between thestorage system block of memory and the main memory block of memory,wherein the storage system block of memory stores storage system dataand the main memory block of memory is a main memory of the computingdevice.
 19. The method of claim 16, further comprising, in response tothe request for data: obtaining first data from sub blocks of thestorage system block where aliases have not been severed; and obtainingsecond data from sub blocks of the main memory block where aliases havebeen severed; and combining the first data and the second data torespond to the request for data.
 20. A computer storage medium havingstored thereon computer-executable instructions, which when executed bya computing device, cause the computing device to perform operationscomprising: sending a request for creation of one or more aliasesbetween corresponding sub blocks of first and second blocks of memory;sending a request for data indicating the first block of memory; and inresponse to the request for data, receiving, data from the second blockof memory.